Allow blink deploy to be ran from CI
#28
Conversation
There was a problem hiding this comment.
I think we should require a blink deploy --config $path_to_config_json flag in CI mode. The .blink directory is in .gitignore by default and it's a hassle to add just .blink/config.json to version control. It'd also allow people to deploy to another agent for staging.
| throw new Error( | ||
| "Multiple organizations found. In CI mode, you must first deploy locally to select an organization, " + | ||
| "or set the organization in .blink/config.json" | ||
| ); |
There was a problem hiding this comment.
| throw new Error( | |
| "Multiple organizations found. In CI mode, you must first deploy locally to select an organization, " + | |
| "or set the organization in .blink/config.json" | |
| ); | |
| throw new Error( | |
| "Multiple organizations found. To use CI mode, please deploy in interactive mode first to select an organization and generate .blink/config.json" | |
| ); |
There was a problem hiding this comment.
@kylecarbs any chance to merge that one in?
There was a problem hiding this comment.
I think we need a little bit of backend work to make this usable. Right now our web UI doesn't offer a way to generate/manage API keys. While technically you could copy the generated credentials after you run blink login into CI variables, they only last 30 days and are irrevocable.
hugodutka
force-pushed
the
ciable
branch
2 times, most recently
from
272acc5 to
175fed6
Compare
3 participants
No description provided.